i selected node 156, but it keeps deploying on node 313 which fails https://www.loom.com/share/625d1cd017cd40fda4cb3fe0d800ed75?sid=024f700b-dd09-433b-b3e9-f981ece2d183

Thanks for testing. I can't reproduce on my end. Deployed on node 156 devnet:

As I understand the issue your encountered is with the gateway, not the deployment per se.

@amiraabouhadid @maayarosama thanks for the review. Lmk if anything else is needed.

Works fine

Thanks @maayarosama for the review + approval. One more to go!

Lmk anyone if anything else is needed.

Update

• I started working directly on the GPU version
• The flist full vm gpu version is done and approved
• I am finalizing the dashboard app (only need to add the gateway domain section and I will make the PR as ready for review)

Update

• We decided to publish right away the GPU version of the app, instead of CPU only
• For this we needed to use a full VM instead (the flist full vm version works 100% and is already accepted in tf-images repo)
• WIP (see below)
• Note: I will get rid of unused variables when I find the gateway fix (failed Lint test)

TODO

• All that is left to do is to finalize the logic for the gateway domain (with port 8080) and custom domain (with port 8080). This means also adding the envs variable OPENWEBUI_DOMAIN.
• Ideally we can present this at ETH Denver. I think I can find the fix on my own, but if devs have any time to check on Monday, it would be VERY appreciated as I am sure you guys can know quickly what I am missing. @xmonader. That being said, I can find it with enough time on my side. Thanks!

Update

The PR is ready for review with GPU version.

• Scott fixed the web gateway flow.
• We confirmed with Scott that the env var was the issue, see here: 🐞 [Bug]: Dashboard App with Full VM GPU Can't take Envs variable e.g. domain #3908
  • So for now we don't have the button Access Domain, but show the domain URL when the deployment is successful (successful message shows ${domain}
• The app works for gpu or cpu, tested on 2 nvidia nodes, e.g. node 7510
  • Note that node 7510 on mainnet shows as shared sometimes. To take into account if you test it. See here: 🐞 [Bug]: Reserve a node as dedicated, then un-reserve it, it appears as shared and not dedicated #3906